SherbyNet - /page/wikibook/entry.mu

<!DOCTYPE html>

<title>Debug code</title>

</head>

Debug code

</h1>

</header>

<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr">Debug code is <a href="Source_code" title="Source code">computer code</a> introduced to a <a href="Computer_program" title="Computer program">computer program</a> to test for errors or to help determine the cause of an error. It can be as simple as an <a href="Echo_(command)" title="Echo (command)">echo command</a> to print the value of a variable at certain points of a program. Modern <a href="Integrated_development_environment" title="Integrated development environment">integrated development environments</a> sometimes render this unnecessary by allowing the placement of stop points at specific places in the program, and providing the ability to view the value of variables through the IDE rather than program output.

<div class="mw-heading mw-heading2"><h2 id="Uses_of_debug_code">Uses of debug code</h2></div>

Debug code's main function is to help <a href="Debugging" title="Debugging">debug</a> code. This can do this in several ways, such as using print statements, assert commands and unit testing.

<div class="mw-heading mw-heading3"><h3 id="Use_in_coding">Use in coding</h3></div>

Small statements can be added to code in order to find the presence and the location of bugs within a program. It can also be used to provide test inputs to simulate possible use cases that a program might need to be able to accept. It can also be used as a place holder for code that is still in development.

<div class="mw-heading mw-heading3"><h3 id="Use_in_video_games">Use in video games</h3></div>

Many video gaming mod, <a href="Cheat_code" class="mw-redirect" title="Cheat code">cheat codes</a>, such as level cheat code, <a href="Glossary_of_video_game_terms#God_mode" title="Glossary of video game terms">invincibility</a>, etc. were originally introduced as debug code to allow the programmers and/or testers to skip hindrances that would prevent them from rapidly getting to parts of the game that needed to be tested; and in these cases <a href="Cheat_mode" class="mw-redirect" title="Cheat mode">cheat modes</a> are often referred to as debugging mode.

It is recommended as a <a href="Best_practice" title="Best practice">best practice</a> that debugging code be removed from production versions of applications, as it can slow them down.<a href="#cite_note-1">[1]</a> However some games leave these commands and cheats available for the players to use as a way to enhance their play experience. For example, the PC version of <a href="The_Elder_Scrolls_V%3A_Skyrim" title="The Elder Scrolls V: Skyrim">The Elder Scrolls V: Skyrim</a> allows the player access to the command console, giving them the ability to modify certain aspects of their game as it is being run. These commands include giving the player invincibility, teleportation and unlimited gold.<a href="#cite_note-2">[2]</a>

<div class="mw-heading mw-heading2"><h2 id="Examples_of_debug_code">Examples of debug code</h2></div>

<div class="mw-heading mw-heading3"><h3 id="Print_debugging">Print debugging</h3></div>

Print debugging is making use of print statements in order to find and isolate bugs in a program. It can be used to track the flow of data values of a piece of code. This type of debug code has some distinct disadvantages. It is temporary and usually removed when the bug is solved. The use of many print statements can affect the actual output of a program and slow down the run-time, depending on how often print statements are called. In some cases print statements do not help find the problem, for example the <a href="C%2B%2B" title="C++">C++</a> stdout has a <a href="Data_buffer" title="Data buffer">buffered</a> output, and sometimes the contents of the buffer are lost leading to incorrect debugging information.<a href="#cite_note-3">[3]</a>

<div class="mw-heading mw-heading4"><h4 id="C++_example">C++ example</h4></div>

<div class="mw-highlight mw-highlight-lang-cpp mw-content-ltr" dir="ltr"><pre>void TestFunction(int timesToRun) {

cout << "the algorithm should run " << timesToRun << " times" << std::endl;

for (int i = 0; i <= timesToRun; i++) {

// run algorithm

algorithm();

// debug print statement

cout << "algorithm run " << i++ << " times." << std::endl;

}

}

</pre></div>

There is a bug in the above code. On an input of 5 the program should print the following to the console.

<pre>the algorithm should run 5 times

algorithm run 1 times.

algorithm run 2 times.

algorithm run 3 times.

algorithm run 4 times.

algorithm run 5 times.

</pre>

The actual output is the following, which is incorrect.

<pre>the algorithm should run 5 times

algorithm run 1 times.

algorithm run 2 times.

algorithm run 3 times.

algorithm run 4 times.

algorithm run 5 times.

algorithm run 6 times.

</pre>

Our function is running through the algorithm an extra time, and upon closer inspection it is clear that our loop is coded wrong.

<div class="mw-heading mw-heading3"><h3 id="Assert_statements">Assert statements</h3></div>

Usually the best time to fix a bug is before the program is run. This can be done by inserting assertions into the code. In C this can be done using the assert() command. An assert command can check to see if the program is running the correct conditions at this point in the program.<a href="#cite_note-4">[4]</a>

<div class="mw-heading mw-heading4"><h4 id="C_example">C example</h4></div>

<div class="mw-highlight mw-highlight-lang-c mw-content-ltr" dir="ltr"><pre>int i, a[10];

for (i = 0; i < 10; ++i)

{

a[i] = 10-i;

}

for (i = 0; i < 10; ++i)

{

a[a[i]] = a[i];

}

</pre></div>

The above code will cause has an out of bounds error which can lead to some unexpected results. The code can be written in a safer way, using assertions, as shown below.

<div class="mw-highlight mw-highlight-lang-c mw-content-ltr" dir="ltr"><pre>#include <assert.h>

int i, a[10];

for (i = 0; i < 10; ++i)

{

assert(0 <= i && i < 10);

a[i] = 10-i;

}

for (i = 0; i < 10; ++i)

{

assert(0 <= i && i < 10);

assert(0 <= a[i] && a[i] < 10);

a[a[i]] = a[i];

}

</pre></div>

<div class="mw-heading mw-heading3"><h3 id="JUnit">JUnit</h3></div>

<a href="JUnit" title="JUnit">JUnit</a> is a simple framework used to write repeatable test available for java, and allows programmers to create their own unit test. A unit test is code that is written to execute a specific function in the code to be tested and usually targets a small unit of code, such a single method or class. Using a combination of assert statements and other test statements, programmers can create suites of test cases in order to tell if a method or function is being executed properly.<a href="#cite_note-5">[5]</a>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20100402234847/http://aspnetresources.com/articles/debug_code_in_production.aspx">"Archived copy"</a>. Archived from <a rel="nofollow" class="external text" href="http://aspnetresources.com/articles/debug_code_in_production.aspx">the original</a> on 2010-04-02. Retrieved 2010-03-26.</cite><code class="cs1-code">{{cite web}}</code>: CS1 maint: archived copy as title (link)

</li>

<li id="cite_note-2"><a href="#cite_ref-2">^</a> <cite id="CITEREFGamer2021" class="citation web cs1">Gamer, P. C. (10 November 2021). <a rel="nofollow" class="external text" href="http://www.pcgamer.com/2011/11/16/skyrim-console-commands-let-you-cheat-and-do-other-stuff/">"Skyrim console commands: Become a giant, a ghost, or a living god"</a>. PC Gamer.</cite>

</li>

<li id="cite_note-3"><a href="#cite_ref-3">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20020817025811/http://oopweb.com/CPP/Documents/DebugCPP/Volume/techniques.html">"Debugging techniques"</a>. oopweb.com. Archived from <a rel="nofollow" class="external text" href="http://oopweb.com/CPP/Documents/DebugCPP/Volume/techniques.html">the original</a> on 2002-08-17.</cite>

</li>

<li id="cite_note-4"><a href="#cite_ref-4">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.csd.uwo.ca/~jamie/C/Debug/UGCS_CS2_debugging_notes.html">"V-Business Card"</a>.</cite>

</li>

<li id="cite_note-5"><a href="#cite_ref-5">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://junit.org/">"Home"</a>. junit.org.</cite>

</li>

</ol></div></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2024-10-01" href="https://en.wikipedia.org/wiki/?title=Debug_code&oldid=1248878734">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>